OpenEdge Application Server overview
Figure 2–1 shows an overview of the OpenEdge Application Server architecture.
This architectural overview shows the Application Server in context, with the shaded areas representing OpenEdge components. The solid one-way arrows show access relationships between “client” (start of arrow) and “server” (point of arrow) components. The dotted arrows show alternate access relationships. For example, Progress 4GL Web services represent an alternate access route between clients and the AppServer. The fat two-way arrows show key intermediate processes through which certain clients must communicate in order to access the OpenEdge Application Server.
The OpenEdge Application Server itself consists essentially of the AppServer (see the "Understanding the AppServer" section), WebSpeed (see the "Understanding WebSpeed" section), and associated adapters (not shown) that enhance or make possible access between certain client types and the AppServer. For example, Progress 4GL Web services depend on an adapter to deploy, manage, and provide access to them from industry Web service clients. In this case, the adapter also encapsulates the Open Client interface required to allow AppServer application services to be accessed by Web service clients. For more information on the adapters for the AppServer, see the "AppServer adapters overview" section. Another section (the "Understanding WebSpeed" section) describes the supported client types for the OpenEdge Application Server.
Note that the AppServer and WebSpeed Transaction Server are shown both as application server components and as clients of the ultimate OpenEdge Application Server component, the AppServer. Note also that OpenEdge data sources can be accessed by any Progress 4GL component except the WebClient™. Finally, note that Progress 4GL Web services are shown both in relation to the OpenEdge Application Server and as the industry Web services that are provided by OpenEdge.
From the overall architecture, you can see that the OpenEdge Application Server is accessible in one way or another from most industry clients, and the OpenEdge Application Server itself can access other application servers in the form of industry Web services. This shows much of the open technology inherent in the OpenEdge platform.
All of the OpenEdge components in this architecture also provide options for security that depend on the component and its function, including features for implementing password-based authentication, encryption of code and data, and data privacy on connections between components using HTTPS on the Internet or an OpenEdge Secure Sockets Layer (SSL) implementation on the intranet. For more information, see OpenEdge Getting Started: Core Business Services .
Note: While OpenEdge does support SSL connections to the OpenEdge RDBMS, OpenEdge does not support SSL connections from Progress 4GL applications to DataServers.